Testing and drift testing #65
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for noir-vite-hardhat canceled.
|
critesjosh
approved these changes
Dec 19, 2023
critesjosh
reviewed
Dec 19, 2023
There was a problem hiding this comment.
cc @catmcgee as this may be a useful reference for seeing how to get the latest release info from an external repo.
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR introduces some drift testing for noir starter.
Problem*
The task of understanding whether noir-starter was still relevant was very much dependent on people telling us that. Which means at least one person will potentially already be blocked by it.
We want to reduce that to a minimum, so this PR will run every night and attempt to build master with the latest stable. If it fails, we can configure alerts and know.
The script is also grabbing all the prereleases. It would be cool to have these tests run on every prerelease so we know in advance when the next stable will break. But that doesn't necessarily help us, we can't update the boilerplate in advance otherwise master will break 😄 Could still be useful to know it will break soon, so we can already start working on a branch